Security for .NET is role-based. Role-based security improves administrative efficiency and supports the seamless integration of security for third-party products used with iMIS. All components in the Central Object Repository honor role-based security (as do the process definitions saved within the CORE). Each user's access to the CORE is dependent on the security privileges of the user.
Define security privileges for roles and groups, and then assign the appropriate roles and groups to individual users. Roles, which are global and used strictly for security purposes, are defined on the Security Administration - Roles page. Groups are defined at the application level.
Note: Record-level security is administered at the application level.
Example of security administration roles
Administering Roles at a Glance
Process for administering security roles
To prevent module administrators from accessing applications
Prevent module administrators from accessing specific module-level applications by doing the following:
Tips for administering roles
Note: Deleting a custom role purges all records related to the role, including any user assignments and privileges granted to the role.
10.6 Production Release. Updated 2/20/2006 1:17:29 PM
© 2009 by Advanced Solutions International, Inc.
All rights reserved.